<text><span class="style12">THER</span><span class="style11">A miscellany of nice little things...The old Type 1 / Type 2 snd resource distinction is now obsolete: HyperCard can play both.The Ask/Answer dialog boxes are now not so restricted as to size and length of text; they now vary in size.A great number of printing options have been added. These are visible in the menus and documented in the Help stacks, and not worth itemising here; but the point is to make HyperCard easier to use as a database from which to print "reports".That's about it: have fun!</span></text>
</content>
<name></name>
<script></script>
</card>
card_7053.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ILE MANAGEMENT</span><span class="style11">File management from HyperTalk has been much improved. You can now have Hypertalk </span><span class="style12">create</span><span class="style11"> a stack without going through the menu (which flashes a dialog box and puts the burden of activity on the user): the basic syntax is:create stack <stack exp> [with <bkgnd exp]. You can have Hypertalk </span><span class="style12">save</span><span class="style11"> a stack. You can use a new command, </span><span class="style12">ask file</span><span class="style11">, to bring up the standard Mac dialog box (PutFile) for saving a file.Also, this is as a good a place as any to mention that even if you DO perform some function through the doMenu command, you can now bypass the confirmation dialog box by the addition "without dialog".Partial pathnames are now supported.</span></text>
</content>
<name></name>
<script></script>
</card>
card_7186.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">YPERTALK OPERATORS</span><span class="style11">Two sets of boolean expression operators make boolean checking far more powerful.The valuable typological operators </span><span class="style12">is a</span><span class="style11"> and </span><span class="style12">is not a </span><span class="style11">have been added to allow checking as to whether something is a number, integer, point, rect, date, or logical.Similarly, there are now existential operators </span><span class="style12">there is a </span><span class="style11">and </span><span class="style12">there is no</span><span class="style11">, which can check to see whether there already exists a window, menu, menuItem, file, button, field, card, background, or stack of a given specification. This last is important. You cannot use the boolean expression "there is a marked card", but you CAN use the boolean expression "there is a NEXT marked card", which gives the result you wanted. </span></text>
</content>
<name></name>
<script></script>
</card>
card_6082.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">YPERTALK COMMANDS</span><span class="style11">The commands for </span><span class="style12">marking</span><span class="style11"> cards take the following syntax:mark <card expression>mark cards where <boolean expr>mark cards by finding <search string>mark all cards(and unmark, correspondingly)It is not hard to see that this is a very powerful addition. Since the "marked" of a card can be made a criterion for doing just about anything, and especially since this criterion is included as a syntax item in "go", "find", "sort" and "print" operations, an important all-purpose selection tool is clearly made available.</span><span class="style12">go</span><span class="style11"> now takes as argument any card, background, or stack expression; the concept "card expression" now includes the specification "marked card". After a stack expression you can also add the phrase "in new window" to keep the current stack from closing. However, there are still some syntax quirks and buggy implementations. For example, you can "go next marked card" and "go next card of this background", but you cannot "go next marked card of this background". Moreover, in the release I'm using, the command "go first marked card" will go to the first card of the stack even if it is NOT marked (a clear bug).</span><span class="style12">sort</span><span class="style11"> capabilties are vastly improved. You can sort cards of a whole stack or of a particular background, and of course "cards" could be restricted to "marked cards". You can sort lines or items of a container. And, after the basic command, you can add specifying parameters: ascending / descending;text / numeric / international / datetime;and finally, an expression that you </span><span class="style13">must</span><span class="style11"> add if you are sorting cards, "by...", which tells the sorter what it is actually to look at to determine the new order. You can sort by just about anything that has any kind of value, numeric, alphabetic, boolean, or what have you. </span></text>
</content>
<name></name>
<script></script>
</card>
card_5513.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ESSAGES</span><span class="style11">New system messages are: </span><span class="style12">ExitField</span><span class="style11">, sent when the cursor was a text-insertion pointer in a field, and the mouse is moved outside the field (the old message, </span><span class="style12">CloseField</span><span class="style11">, is sent only when there was also a </span><span class="style13">change</span><span class="style11"> during this session in the field); </span><span class="style12">keyDown</span><span class="style11">, which passes as a parameter the value of the key that was pressed, and (if the command-key was held at the same time) </span><span class="style12">commandKeyDown</span><span class="style11">; </span><span class="style12">suspendStack</span><span class="style11"> and </span><span class="style12">resumeStack</span><span class="style11">, already dealt with above; and </span><span class="style12">startUp</span><span class="style11">, sent to the first card of a stack, if it is the first stack opened when HyperCard starts up, </span><span class="style13">before</span><span class="style11"> the stack really opens, so you can perform preparatory activities without their being seen on the screen.It is now possible to modify the </span><span class="style12">message hierarchy</span><span class="style11">. In particular, you can </span><span class="style13">insert</span><span class="style11"> a stack (up to 10) into the series of things that the system checks when it receives a message: this insertion takes place, in the series, just before Home. An important value of this is that you can use it to bypass the 30K character limit on scripts. It also may be that this is just a more convenient way to group and access things: if 20 stacks need to use a handler doCrud, but you don't want to include it in all of them or in Home, you could include it in a stack of its own and just insert that special stack into the hierarchy. And it isn't just a matter of scripts, either: insertion of a stack into the hierarchy makes all its resources available as well. The command is: </span><span class="style13">start using stack <stack exp></span><span class="style11">. For removal: stop using... ΓÇö A list of all stacks inserted in this way can be obtained from the Property stacksInUse; the list is return-delineated, so you can only look at a line at a time from the msg box.The order in which system messages are sent when a situation calls for more than one has been modified; this is important, but too technical to go into here. </span></text>
</content>
<name></name>
<script></script>
</card>
card_5323.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">EVELOPMENT TOOLS</span><span class="style11">There is now an ICON EDITOR under the Edit menu, for creating and editing icons. It is very intuitive to use, and you can draw, modify, and pick up from existing art. Since icons are of tremendous value both for buttons and for animation, this feature should be regarded as a major advance.There is also now a decent SCRIPT EDITOR for writing in Hypertalk. It scrolls both horizontally and vertically; it has better cursor and mouse control than the old editor; it permits more than one (resizeable) window open at once; it includes an improved Find dialog box, with a new find selection command and two new search-and-replace commands; and it has a number of other commands that you can find out about by examining the menus when you are looking at a script. (The script editor's default font is now a Property, scriptTextFont.)The script editor now also comes with heavy debugging capabilities. When you combine these with the new ability to keep multiple windows open and switch between them easily, you are going to wonder how you ever lived without them if you write scripts of any complexity at all. There are two "secret" debug windows, "Message Watcher" and "Variable Watcher", which can be summoned up independently ("mw", "vw"), or from the menu as part of a debug operation. You can start a debug operation from within a script if it contains the words "debug checkpoint" or by using Set Checkpoint from the Script menu; or, if a handler is actually running, by hitting option-command-period. Also, a run-time script error provides Debug as an option.Commands from within a debug situation are available on a menu or as keyboard commands; these include Step (within current handler), Step Into (all handlers), Trace and Trace Into (you can set the Delay to make it easier to watch), Set Checkpoint, Abort (kill the debugger and let me edit the script), and Go (kill the debugger and resume execution).The Message Watcher has a nextLine property, and your script can set this to insert a message about where it is into the stream. Unfortunately its operation is currently rather buggy. The Variable Watcher allows you to examine and even edit variable values values; you can also readjust its bar locations. A script is now not saved into its stack until you demand explicitly that this be done. From within a script, you save and close the script window with ENTER; or you can just save with command-S; or you can save and then switch windows, leaving the script open but backgrounded, with command-S command-L. In line with HyperCard's "open system" orientation, the script editor and debuggers are plug-ins, meaning that if third parties write alternatives, a simple setting of a global variable will cause these to be used instead of the ones included with HyperCard. </span></text>
</content>
<name></name>
<script></script>
</card>
card_4503.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">TACK CAPABILITIES</span><span class="style11">Stacks have two new properties for PROTECTION:Can't Abort disables command-period interrupts;Can't Peek disables using command-option to find buttons and fields.</span><span class="style12"></span><span class="style11">Another new protection device is the Ask Password command from HyperTalk. This is just like the old Ask command, but the reply is illegible on the screen and is sent to IT encoded. You could save IT in a hidden text field someplace and refer to it as a protection scheme later.</span><span class="style12"></span></text>
</content>
<name></name>
<script></script>
</card>
card_6323.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ARD CAPABILITIES</span><span class="style11">A card can now be MARKED, and whether or not a card is marked can be made a criterion during a search, a sort, or a go operation. The value of this is obvious and pervasive. You can set this property by hand in the Card Info box, or you can do it powerfully from a script (discussed further later...).DONT SEARCH can also be used to exclude an entire card from searching.</span></text>
</content>
<name></name>
<script></script>
</card>
card_4935.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">UTTON CAPABILITIES</span><span class="style11">There is now a SHARED HILITE property for background buttons. This allows you to choose whether or not the hilite of a bg btn is to be true for every card of that background. This </span><span class="style13">used</span><span class="style11"> to be </span><span class="style13">automatically</span><span class="style11"> so, but now you have a choice.</span></text>
</content>
<name></name>
<script></script>
</card>
card_4664.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">IELD CAPABILITIES</span><span class="style11">You may now have </span><span class="style16">MULTIPLE FONTS</span><span class="style11"> (see?) within a single field; you can also have multiple STYLES, (the bold title above is an example), and these are available not only from the Style menu but also as command-shift shortcuts, just as in a word processor. The field still has a basic font and style. If you use different font SIZES, line height adjustment will be automatic unless you check off Fixed Line Height.DONT WRAP disables word wrap within the field. The purpose of this is to ensure the integrity of a relationship between </span><span class="style13">physical</span><span class="style11"> line-number and </span><span class="style13">actual</span><span class="style11"> line-number (based on a count of Return characters).DONT SEARCH excludes the field from searches (duh). When you consider that in the old Hypercard, you could restrict a search to a </span><span class="style13">single</span><span class="style11"> field, but otherwise you were compelled to search </span><span class="style13">every</span><span class="style11"> field, the value of this is obvious.SHARED TEXT. A property of bg fields only: allows you to enter or alter text in the field just once and have it reflect in the text of all the corresponding fields of the other cards throughout the background. Shared Text is automatically Locked, and can be edited only by entering Background mode; it is also automatically Dont Search. -- Actually, the situation is more complex. Every bg field now has TWO sets of text: its own, and the shared text. You can only SEE one at a time, and the Shared Text box toggles which you will see. But they are both always there. This fact could be used in some interesting way, one suspects...GROUP TEXT. Used in connection with the new ClickText feature: causes the ClickText to be the whole phrase that has been grouped, and not just a single word. This is to enable pseudo- Hypertext. A pair of HyperTalk commands, </span><span class="style13">show groups</span><span class="style11"> and </span><span class="style13">hide groups</span><span class="style11">, cause a grey underline to appear beneath grouped text; the default on startup of a stack, however, is that no such underline appears.When a user clicks on text in a field, three functional expressions are evaluated: </span><span class="style12">the clickChunk, the clickLine, </span><span class="style11">and </span><span class="style12">the clickText</span><span class="style11">. The clickText is the literal text, which will be a word or (if Grouped) a group. The clickChunk, like the old foundChunk, is a complex statement about where this text is, in the form "char M to N of card/bkgnd field X". This is how the effect on the previous page was accomplished. </span></text>
</content>
<name></name>
<script></script>
</card>
card_6511.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ILIEU ΓÇö Visuals</span><span class="style11">There are two new visual effects: stretch and shrink. You can </span><span class="style12">stretch</span><span class="style11"> or </span><span class="style12">shrink</span><span class="style11"> to or from top, center, or bottom. To see an example click on the word "stretch" or "shrink" above.The Button Info dialog box which appears when you create a button now contains an EFFECT option which summons a menu of many of the available visual effects and allows you to attach one to your button. This is of value only if you are creating very simple buttons using the LinkTo option, without HyperTalk.</span></text>
</content>
<name></name>
<script></script>
</card>
card_6895.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ILIEU ΓÇö Menus</span><span class="style11">HyperCard now can manipulate another standard Mac object, MENUS. There is only one menubar, and it is a property, as it were, of the computer, not of this or that stack; but every item along it (File, Edit, etc.) is called a Menu, and it can be deleted, it can be modified (changing what appears when you click on the menu name), and new menus can be added to the right, by your program at any time. ΓÇö You will observe the addition of an example menu at the right of the menubar; you can play with it, but none of its options is functional, fortunately.Caution: if you remove a menu item, you remove the user's ability to access that item </span><span class="style13">in any way</span><span class="style11">, including command-key combinations. However, no change is permanent: the command </span><span class="style12">reset menubar</span><span class="style11"> restores the standard settings.A sort of all-purpose menu-maker is included in the Power Tools.A menu is a container, like a field, and it is specified by the typological word </span><span class="style13">menu</span><span class="style11">. You create a menu with</span><span class="style13"> create menu "menu".</span><span class="style11"> Once a menu exists, every single line within it is considered an item, and you can delete items, or put into, before, and after, item whatever of menu "menu", just as you would with any other container. If you add menu items, you presumably want some action taken when the user selects that item. You can ensure this by specifying a menu message (menuMsg) for that item at the time you put it into the menu. For example, </span><span class="style13">put "Explode" into menu "Panic" with menuMsg "doExplode"</span><span class="style11">. You would then have a handler in a script someplace, beginning "on doExplode...". Menu items have properties which you can set with the </span><span class="style13">set...to...</span><span class="style11"> command. These are: name; textStyle; commandChar; enabled (true or false); checkMark (true or false); and menuMsg.The simplest way to modify a menu is thus to do it at OpenStack time. But BEWARE: remember to </span><span class="style13">reset menubar</span><span class="style11"> at CloseStack time!!!! Otherwise, your modified menu may still be there in when the user is in a different stack!</span></text>
</content>
<name></name>
<script></script>
</card>
card_5851.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ILIEU ΓÇö Windows</span><span class="style11">Both Palettes and Sizing are really subsets of the fact that HyperCard now thinks in terms of WINDOWS. This broad fact has many other implications. More than one stack can now be open at the same time, because (as with many other applications, such as a word processor) multiple windows can exist laid on top of one another (or, if you have room on the screen, not on top of one another).This new Window orientation of stacks has required the addition of two new System Messages: </span><span class="style12">suspendStack</span><span class="style11"> and </span><span class="style12">resumeStack</span><span class="style11">, sent when you "leave" and "return to" a stack left open as a window.A Picture is a window, and since you can now have windows, you can now show pictures. A picture eligible for such display may be a PICT resource, or it may be a PICT or MacPaint file, or it may be something in the clipboard. The management of these pictures allows very powerful effects, but it is too complex to describe here. Suffice it to say that there are a lot of new Picture commands.As a sort of side-effect of this, you can now actually show and hide the picture-layer of cards other than the one you are in: that is, you can give the command </span><span class="style13">show</span><span class="style11"> (or hide) </span><span class="style13">pict of</span><span class="style11">... followed by a card or background expression.All current windows are listed in a sytem function, </span><span class="style12">the windows</span><span class="style11">, delimited by Returns. This list contains some surprising items, since certain windows are always open but invisible. The windows are listed in "receding" order.To find out what windows are open now, summon the msg box (from the navigator palette) and type "line 1 of the windows", and keep doing this, increasing the line number, until you get no response.This raises an important distinction. You can close a window (including a palette) by the command </span><span class="style13">send close to window "name"</span><span class="style11">. This frees up memory. But you can also </span><span class="style13">show</span><span class="style11"> and </span><span class="style13">hide</span><span class="style11"> a window, without closing it.You can make your window appear at any location. Bear in mind that the location specified is the upper left corner of the window, and that you are operating relative to the HyperCard window, not the screen, except for the card window, which </span><span class="style13">is</span><span class="style11"> relative to the screen. </span></text>
</content>
<name></name>
<script></script>
</card>
card_4166.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ILIEU ΓÇö Card Sizing</span><span class="style11">Cards are now SIZEABLE. Minimum is 64x64. You can size at stack creation time, or you can resize later (not recommended, though, because it may hide features of your card and make them unavailable) by choosing Resize from Stack Info.You can select standard sizes, or create your own by using the lower left corner of the picture as a handle. If the card is too big for the screen, you can scroll to see the rest of it using the scroll palette from the GO menu (click and drag the hand icon).For example, this card is an unusual shape and size. Its window is very small, and floats in front of whatever background you already has on your screen. On the other hand, the card itself is too big for the window, and has to be scrolled if the user is to see the bottom. The scroll palette is floating to the lower left of this window, so you can try it. </span></text>
</content>
<name></name>
<script></script>
</card>
card_3041.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ILIEU</span><span class="style11">PALETTES. You can now create your own palettes (floating, movable windows) using the Palette Maker. As a result, many stacks now have palettes as an additional resource for helping the user get around.There is a new, "secret" palette, the Navigator, available by typing "nav" into the msg box. It duplicates the GO menu in button form.</span></text>
</content>
<content>
<layer>background</layer>
<id>34</id>
<text><span class="style12">ILIEU ΓÇö Palettes</span><span class="style11">You can now create your own PALETTES, using palette maker. A Palette is a movable window, attached as a resource to a stack, that always appears in front of everything else. It can contain art; it can also contain buttons that send messages. As a result, palettes are now an important way to provide a user with options. In effect they are a customized dialog box.An important palette, in this regard, is "nav", the Navigator (type "nav" into msg). This stack, for example, has NO navigational buttons except those already in the navigator palette, which floats to the left. You can click on the buttons, and move the palette around; but if you click the go-away box, you'll have to rely entirely on the menu for navigation (so don't).Palettes are rather complicated to create, but the job has been made simpler by the inclusion of a Power Tool in the Home Stack, Palette Maker.You cause a palette to appear first by the command </span><span class="style13">palette "name","location"</span><span class="style11">. After that, the palette is a window: you can dismiss it completely by the command </span><span class="style13">send "close" to window "name"</span><span class="style11">, or you can just render it visible or invisible with the hide/show command, e.g. </span><span class="style13">hide window "name"</span><span class="style11">. </span></text>
</content>
<name></name>
<script></script>
</card>
card_8058.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">ILIEU ΓÇö Speed</span><span class="style11">HyperTalk is now a compiled language. Before a handler is run for the first time, HyperCard holds a sort of dry run session, in which it looks over the handler and translates it into a form which needs far less interpretation in order to run ΓÇö and therefore can run very quickly. This compiled version of the handler is then held in memoryas long as there is room.This means that HyperCard runs noticeably faster than it used to. It is true that actions involving navigating through objects in various cards, redrawing the screen, and other things that involve complicated behaviours outside of the script itself, still slow things down quite a bit. But on the whole the increased speed means that a script can be long and complex without slowing things down very much; and this will mean a much more powerful environment. </span></text>
</content>
<name></name>
<script></script>
</card>
card_8392.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style12">NTRODUCTION</span><span class="style11">In the new HyperCard (version 2.0), no overview of what is new is included. This is a major failing, since the upgrade is drastic. This little handbook describes (and in a few cases illustrates) what you may expect to see in the new HyperCard. Not all changes are listed, just some (subjectively) important ones.I cannot resist throwing in my little opinion at this point. The look-and-feel of HyperCard has definitely been overhauled to get rid of its sluggishness, its clumsiness, its simple-mindedness. Evidently wherever developers and users have complained to Apple, "How foolish it is that HyperCard can't do </span><span class="style15">this</span><span class="style11">," Apple has listened. Functions that had to be performed with huge, complicated scripts, or with attached XCMDs written in a low-level language, have now been simply included directly in HyperCard. As a result, a tremendous number of the obvious failings of the old HyperCard are gone, and many new capabilities more in line with the power of the Macintosh environment generally have been added. You can sense this directly from the look and feel of products written in the new HyperCard: the lines are sleeker, both literally and metaphorically. There's no doubt about it: this is what HyperCard should have been all along.However, HyperCard is still a quirky, buggy milieu. From the user end things are mostly just smoother and more impressive (although it bothers me that the user still doesn't know where the clickable places on the screen are ΓÇö the cursor doesn't change when it is over them, for example, though of course it can be programmed to do so). But the script author still runs up against strange brick walls all the time. HyperTalk itself remains more difficult than it needs to be, because of a number of weird inconsistencies of its cantankerous syntax. (I have to "set" some sorts of items and "put" others, but I can "get" either one.) The management of sets of radio buttons has not been made any easier. Sorting is improved, but general string manipulation is as feeble as ever. The simulation of HyperText is made easier, but real HyperText ("anything can be a button") is still absent. The dividing line between what you can always "get" and what you can only "get" by first "go"-ing remains murky. A stack can be told do something when it is being closed, but it cannot make this action dependent on </span><span class="style13">why</span><span class="style11"> it is being closed (e.g., on what stack is about to be opened). The list goes on. In sum: in many ways HyperCard 2.0 is an all-new machine, and it certainly puts the old HyperCard in the shade; but don't get your hopes up too high: it still has some very odd, prickly places to it. Things are great, but they might have been considerably greater. Perhaps in 2.5...?</span></text>
</content>
<name></name>
<script></script>
</card>
card_7591.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>3</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>45</top>
<right>275</right>
<bottom>57</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>4</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>55</top>
<right>275</right>
<bottom>67</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>5</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>65</top>
<right>275</right>
<bottom>77</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>6</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>77</top>
<right>275</right>
<bottom>89</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>7</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>87</top>
<right>275</right>
<bottom>99</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>8</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>99</top>
<right>275</right>
<bottom>111</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>9</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>109</top>
<right>275</right>
<bottom>121</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>10</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>120</top>
<right>275</right>
<bottom>132</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>11</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>131</top>
<right>275</right>
<bottom>143</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>12</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>142</top>
<right>275</right>
<bottom>154</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>13</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>153</top>
<right>275</right>
<bottom>165</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>14</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>164</top>
<right>275</right>
<bottom>176</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>15</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>175</top>
<right>275</right>
<bottom>187</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>16</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>186</top>
<right>275</right>
<bottom>198</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>17</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>198</top>
<right>275</right>
<bottom>210</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>18</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>208</top>
<right>275</right>
<bottom>220</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>19</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>221</top>
<right>275</right>
<bottom>233</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>20</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>232</top>
<right>275</right>
<bottom>244</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>21</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>242</top>
<right>275</right>
<bottom>254</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>22</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>252</top>
<right>275</right>
<bottom>264</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>23</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>263</top>
<right>275</right>
<bottom>275</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>24</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>274</top>
<right>275</right>
<bottom>286</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>25</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>262</left>
<top>287</top>
<right>275</right>
<bottom>299</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29522</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>New Button</name>
<script>on mouseUpput the number of me + 2 into ourLineget line ourLine of cd fld "index"if it is not empty then go card ourLine - 1end mouseUp</script>
</part>
<part>
<id>26</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>28</left>
<top>311</top>
<right>273</right>
<bottom>349</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>26635</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>About this Stack</name>
<script>on mouseUpshow card field "About"end mouseUp</script>
</part>
<part>
<id>27</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>50</left>
<top>9</top>
<right>256</right>
<bottom>295</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>About</name>
<script>on mouseuphide card field "About"end mouseup</script>
<text><span class="style11"></span><span class="style22">The New Hypercard</span><span class="style11"></span><span class="style19">A stack thrown together by Matt Neuburg of the Classics Department of Swarthmore College to teach himself the new features of Hypercard 2.0.This stack may be freely redistributed.No warranty this stack will work, etc.Note that you must use the navigation palette to move around. Click on the plus sign of the appropriate entry on the notebook to display that entry.</span><span class="style21"> Click anywhere to hide this field</span><span class="style19">Praise (only) should be directed to:</span><span class="style17">neuburg@campus.swarthmore.edu</span><span class="style19">Questions, comments, or requests for information about Hypercard and development from tri-college users may be directed to:Matthew WallSwarthmore College Computing Center(215) 328-8506</span><span class="style17">wall@campus.swarthmore.edu</span><span class="style23"> "Anywhere else it would have been an alpha."</span></text>
